Server-side hosted environment for a cloud gaming system

ABSTRACT

The disclosed computer-implemented method may include executing, by a server-side hosted environment, a first application non-native to the server-side hosted environment, the executing comprising virtualizing hardware for the server-side hosted environment that supports the execution of the first application in the server-side hosted environment, receiving, by the server-side hosted environment by way of a network, an input data stream from a second application executing on a computing device, processing, by the server-side hosted environment and by the first application while executing in the virtualized hardware, the input data stream, the processing generating an output data stream, and outputting, by the server-side hosted environment and to the computing device by way of the network, the output data stream for use by the second application. Various other methods, systems, and computer-readable media are also disclosed.

CROSS REFERENCE TO RELATED APPLICATION

This application claims the benefit of U.S. Provisional Application No. 63/194,821 filed on May 28, 2021, and the benefit of U.S. Provisional Application No. 63/105,320 filed on Oct. 25, 2020, the disclosures of which are incorporated, in their entirety, by this reference.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings illustrate a number of exemplary embodiments and are a part of the specification. Together with the following description, these drawings demonstrate and explain various principles of the present disclosure.

FIG. 1 is an illustration of an exemplary system for hosting an application in a server-side environment.

FIG. 2 is an illustration of an exemplary architecture for a server-side hosted environment for a cloud gaming system.

FIG. 3 is an illustration of an example server included in a cloud application platform that hosts an application in a server-side environment.

FIG. 4 is an illustration of an exemplary architecture of a system 400 for providing web real-time communication between a computing device and an application platform included a server-side environment.

FIG. 5 is an illustration of an exemplary architecture for hosting an application in a server-side environment that shows further details of the implementing of the exemplary architecture in data centers that provide the server-side environment.

FIG. 6 is an illustration of an exemplary architecture for hosting an application intended to execute in a first operating system in a server-side environment.

FIG. 7 is an illustration of an exemplary architecture for hosting an application intended to execute in a second operating system in a server-side environment.

FIG. 8 is a flow diagram of an exemplary method for implementing a cloud gaming system in a server-side hosted environment.

FIG. 9 is a block diagram of an example system that includes modules for use in implementing a cloud gaming system in a server-side hosted environment.

FIG. 10 illustrates an exemplary network environment in which aspects of the present disclosure may be implemented.

FIG. 11 is an illustration of exemplary augmented-reality glasses that may be used in connection with embodiments of this disclosure.

FIG. 12 is an illustration of an exemplary virtual-reality headset that may be used in connection with embodiments of this disclosure.

Throughout the drawings, identical reference characters and descriptions indicate similar, but not necessarily identical, elements. While the exemplary embodiments described herein are susceptible to various modifications and alternative forms, specific embodiments have been shown by way of example in the drawings and will be described in detail herein. However, the exemplary embodiments described herein are not intended to be limited to the particular forms disclosed. Rather, the present disclosure covers all modifications, equivalents, and alternatives falling within the scope of the appended claims.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

Many software applications may be hosted in the cloud and delivered to a user remotely. Cloud-based computing technology may allow a user to interact with a local computing device to execute a cloud-hosted application on a remote server. The local computing device may connect to the remote server by way of a network (e.g., via the Internet) to enable the interaction. For example, a cloud-hosted application may be an application, such as a game, that traditionally was executed on a local computing device of an end-user. Examples of local computing devices may include, but are not limited to, mobile computing devices, smartphones, tablets, notebooks, Chromebooks™, laptops, and other personal computing devices (e.g., PCs). The execution environment, architecture, and hardware on a remote server that implements and runs a cloud-hosted system for hosting an application (e.g., the cloud-hosted infrastructure environment) may vary significantly from the execution environment, architecture, and hardware that executes an application on the local computing device (e.g., the locally-hosted infrastructure environment). Based on these differences, an application intended to execute in the cloud may be specifically written as a cloud-hosted application and may be specifically designed to run on a cloud-hosted server to enable adequate performance. Also, an application intended to execute on a local computing device may be specifically written as an on-premise application (a local application) and may be specifically designed to run on the local computing device to enable adequate performance.

In some cases, an application intended to execute on a local computing device may require modifications to execute then in a cloud-hosted infrastructure environment. The modifications may include, but are not limited to, modifications to accommodate various hardware and software differences inherent in the cloud-hosted infrastructure that are different than those of the local computing device. For example, a locally hosted infrastructure environment of the local computing device may include a local display device that does not include or implement layers of virtualization. This may be compared to the cloud-hosted infrastructure environment that may include a headless system that implements one or more virtualized layers more typically found in a server environment that may support a cloud-hosted infrastructure. Due to these various hardware and/or software differences between the locally-hosted infrastructure environment and the cloud-hosted infrastructure environment, a local application may require significant modifications to enable adequate performance and a suitable user experience when executed as a cloud-hosted application executing in the cloud-hosted infrastructure environment.

The present disclosure is generally directed to systems and methods for optimizing the execution of a local application in a cloud-hosted infrastructure environment without the need for modifications to the local application while providing adequate performance and a suitable user experience. For example, the local application may execute in a server-side hosted environment, such as a cloud-hosting infrastructure. As will be explained in greater detail below, embodiments of the present disclosure may optimize the execution of an application non-native to the server-side hosted environment in the server-side hosted environment for effective content delivery to a computing device of an end-user. In some implementations, the application may be designed to run on a computing device of an end-user, such as a mobile computing device or a PC, rather than in a virtualized environment on a server for content delivery over a network. By optimizing the execution of the non-native application in the server-side hosted environment, embodiments of the present disclosure may improve the functioning of computing devices that support the execution of the non-native application in the server-side hosted environment, may allow end-users to use more of a variety of applications with cloud-based systems, may spare application and/or cloud infrastructure developers from having to invest resources in adapting or creating applications specifically for execution in the server-side environment. In addition, or in the alternative, optimizing the execution of the non-native application in the server-side hosted environment may allow for the modifying or enhancing of the application dynamically as it executes in the server-side environment.

Features from any of the embodiments described herein may be used in combination with one another in accordance with the general principles described herein. These and other embodiments, features, and advantages will be more fully understood upon reading the following detailed description in conjunction with the accompanying drawings and claims.

The following will provide, with reference to FIGS. 1-5, detailed descriptions of exemplary architectures for a system that hosts a non-native application in a server-side environment. FIGS. 5-7 provide detailed descriptions of a system that hosts non-native applications by virtualizing and/or emulating the execution environment in a cloud application platform that was intended to run the non-native application. FIG. 8 provides a detailed description executing a non-native application in a server-side hosted environment.

FIG. 1 is an illustration of an exemplary system 100 for hosting an application in a server-side environment. The system 100 may include a cloud application platform 102 communicating with a computing device 106 over a network 104. In some embodiments, the term “server-side” may refer to a classification of resources that run on a server or other suitable platform to generate and/or deliver content over a network to a computing device (e.g., the computing device 106). The cloud application platform 102 may include servers and other software and hardware to host, run, and/or execute an application in the cloud to provide content to the computing device 106. The content may include, but is not limited to, graphics content and audio content.

In some implementations, the network 104 may be the Internet, a Local Area Network (LAN), a Wide Area Network (WAN), or any type of communication network that implements various types of communication protocols and/or physical connections. The computing device 106 may be a client device. For example, a user (e.g., an end-user) may interact with the computing device 106 when interfacing with an application executing in the cloud application platform 102. In addition, or in the alternative, a user may view content provided by the cloud application platform 102 that may be presented on a display device included in the computing device 106. The computing device 106 may receive the content from the cloud application platform 102 in a web browser or other application executing locally on the computing device 106.

A remote device may communicate with, may be connected to (wired or wirelessly), and/or otherwise be interfaced with an input device. For example, the computing device 106 may be in communication with an input device 108. In some implementations, the computing device 106 may include the input device 108. In some implementations, the input device 108 may be in wired or wireless communication with the computing device 106. The wireless communication may be implemented using a wireless communication protocol that may include, but is not limited to, Wi-Fi, BLUETOOTH, cellular, radio, or any other type of wireless communication protocol. The input device 108 may provide input to computing device 106. The computing device 106 may then provide information and data to the cloud application platform 102 by way of the network 104. The cloud application platform 102 may use the information and data to control the application executing in the cloud application platform 102. The control of the application may be based, at least in part, on the input received from input device 108.

A cloud application platform may provide a server-side hosted environment for executing an application (e.g., a cloud-hosted application). For example, the cloud application platform 102 may provide a cloud-hosted infrastructure environment that is architected to include at least one remote server, an execution environment, and hardware for implementing and running a cloud-hosted system for hosting the application. As described in more detail below, the cloud application platform 102 may provide various optimizations to allow for enhanced execution of an application not designed to operate in a server-side hosted environment (e.g., an application non-native to the server-side hosted environment (a non-native application or a local application)).

In some implementations, the cloud application platform 102 may virtualize hardware for the server-side hosted environment that is native to the execution environment of an application. The application may then be executed in the server-side hosted environment, which is not native to the application, by the virtualized hardware. The virtualized hardware may enable the application that is non-native to the server-side hosted environment to execute in the server-side hosted environment. In some implementations, the cloud application platform 102 may intercept network calls from the non-native application as it is executing in the server-side environment. The cloud application platform 102 may map a network call intended for a specified network location in the native execution environment of the application to an updated network location in the server-side hosted environment. In some implementations, the cloud application platform 102 may optimize graphics processing of an application executing in the server-side hosted environment. The cloud application platform 102 may optimize the non-native application by modifying a video frame of the non-native application for transmission to the computing device 106 during a rendering process. For example, the optimization may change a target characteristic of the video frame.

In some implementations, the application may be a game (e.g., a video game, a gaming application). For example, the game may be an existing game designed to execute on a computing device of a user. For example, the game may be a mobile application. The system 100 may host and provide cloud-delivery for an existing game designed for varying hardware and/or software platforms. The cloud-delivery of the existing game may allow a user to play on the game on the computing device of the user without performance degradation and without the need for substantial modifications to the game.

FIG. 2 is an illustration that includes details of an exemplary system 200 for hosting an application in a server-side environment. For example, referring to FIG. 1, the system 200 may include input devices 208, which may include the input device 108. The system 200 may include computing devices 206, which may include the computing device 106. The system 200 may include the network 104. The system 200 may include a cloud application platform. In some implementations, the cloud application platform 202 may represent an implementation of the cloud application platform 102. In some implementations, the system 200 may be a cloud gaming system that hosts game applications in a server-side environment.

An input device may include any suitable device for providing input to a computing device. For example, the input devices 208 may include, but are not limited to, a mouse 210, a keyboard 212, a microphone 214, or a game controller 232. The computing devices 206 may be in communication with (connected to) the input devices 208. The computing devices 206 may connected to the input devices by way of a wireless or a wired connection. The computing devices may be in wired or wireless communication with the input devices 208. The input devices 208 may provide an input stream of data to the computing devices 206 by way of a connection between an input device and a computing device.

A computing device may receive input from an input device. In some implementations, a computing device may include the input device. For example, the computing devices 206 may include, but are not limited to, a mobile computing device 216 (e.g., a smartphone, a tablet, a notebook computer, a Chromebook™), a personal computing device 218 (e.g., a PC), a laptop computer 220, an augmented-reality system 1100, and a virtual reality (VR) system 1200. In some implementations, a touchscreen and/or touchpad included in the mobile computing device 216, the personal computing device 218, and/or the laptop computer 220 may be the source of the input that the computing device provides as information and data to the cloud application platform 202 by way of the network 104.

One or more computing devices may communicate with a cloud application platform by way of a network. For example, the computing devices 206 may communicate with the cloud application platform 202 by way of the network 104. The computing devices 206 may send, transmit, or otherwise provide an input stream of data to the cloud application platform 202. The input data stream may include information and data for controlling the execution of a non-native application that is hosted in the server-side hosted environment of the cloud application platform 202. In response, the cloud application platform 202 may send, transmit or otherwise provide a video and/or audio data stream to the computing devices 206. The video and/or audio data stream may be displayed on a display device of the computing device (e.g., display device 222, display device 224, display device 226, a left display device 1115(A) and a right display device 1115(B) (referring to FIG. 11), and/or one or more electronic displays included in the virtual-reality system 1200 which will be described in more detail with reference to FIG. 12).

A cloud application platform may include a plurality of servers. In the example shown in FIG. 2, the cloud application platform 202 includes three servers 228 a-c. In some implementations, a cloud application platform may include less than three servers (e.g., two servers, one server). In some implementations, a cloud application platform may include more than three servers.

A cloud application platform may utilize edge computing to efficiently receive an input data stream and to efficiently serve content using an output video and/or audio data stream. The receiving and outputting of data streams may be from cloud servers to computing devices by way of a network. In some implementations, the cloud application platform 202 may utilize edge computing to efficiently receive the input data stream and to efficiently serve the video and/or audio data stream (e.g., content) from cloud servers to the computing devices 206 by way of the network 104. Edge computing may bring computational resources of the cloud application platform 202 closer to a user (a computing device of an end-user) increasing the responsiveness and throughput of the non-native application as it executes in the server-side hosted environment. For example, edge node(s) 230 may include one or more edge nodes. An edge node may provide a connection between a server (e.g., one of the servers 228 a-c) and a computing device (e.g., one of the computing devices 206). The edge node may provide service delivery computing offload, internet-of-things (IoT) connection management, storage, and caching. The use of edge computing may create a content delivery network that delivers low latency content from servers (e.g., edge servers) to requesting computing devices.

The system 200 may advantageously allow developers to build applications intended to execute on one computing platform (e.g., operating system) to reach other users operating different computer platforms. and further may provide users with immediate access to applications regardless of device capabilities, such as games, virtual reality (VR) applications for VR systems (e.g., the VR system 1200), augmented reality (AR) applications for AR systems (e.g., the AR system 1100), applications for other types of artificial or augmented reality systems and experiences, and applications that provide streaming media, etc. These advantages may be realized with system 200 by using virtualization technology to run applications in virtual hosting environments on top of a base operating system. Example virtual hosting environments may include, for example, Android™ virtual environments, MICROSOFT® WINDOWS® virtual machine (“VM”), and/or other container technologies.

In some implementations, the system 200 may be a cloud gaming system that hosts game applications in a server-side environment. The use of edge computing may allow the system 200 to meet response-time constraints for real-time gaming in a cloud gaming system by providing real-time responses and interactions resulting in adequate performance for a game along with a suitable user experience when the game is run as a cloud-hosted application executing in a cloud-hosted infrastructure environment.

FIG. 3 is an illustration of an example server 350 included in a cloud application platform that hosts an application in a server-side environment. For example, referring to FIG. 2, the server 350 may be one of the servers 228 a-c in the cloud application platform 202. As described with reference to FIG. 1, a cloud application platform may provide a cloud-hosted infrastructure environment that is architected to include at least one remote server, an execution environment, and hardware for implementing and running a cloud-hosted system for hosting the application. The server 350 may include hardware, firmware, and/or software for hosting an application in a server-side environment.

A server may execute an operating system. For example, the server 350 may execute an operating system 302 in communication with, and running on, one or more central processing units (CPUs) 304 a-n. The operating system 302 may also be in communication with one or more graphics processing units (GPUs) 306 a-n for image and graphics processing. The server 350 may include any suitable number of CPUs 304 a-n and GPUs 306 a-n.

An operating system may interact with one or more edge nodes in an edge computing environment. For example, the operating system 302 may be an operating system that interacts with edge nodes (e.g., the edge node(s) 230) in an edge computing environment. The operating system 302 may include a virtualization module 308 that provides software and operating system virtualization capabilities that allow the cloud application platform 202 to support multiple, isolated virtual environments. In some implementations, the virtualization module 308 may be a virtual machine (e.g., a Kernel-based Virtual Machine (KVM)). In some implementations, the virtualization module 308 may be an emulator (e.g., a Quick EMUlator (QEMU)).

A container may include an application layer that packages code, dependencies, and configuration files together to create an entire runtime environment for the container. For example, any suitable container may be used such as a container system that may include a base operating system layer and a customization layer included in a hosted environment, and an application layer. The operating system 302 and the virtualization module 308 may support one or more containers 310 a-n. Each container 310 a-n may be a virtualized software unit that provides an isolated environment for software execution. Each container 310 a-n may provide a sandboxed environment to execute a respective hosted environment 312 a-n. Likewise, each hosted environment 312 a-n may, in turn, execute a respective application 314 a-n. In some implementations, a hosted environment may be a containerized operating system. In some implementations, a hosted environment may be an emulator that emulates a specific operating system. Nonlimiting examples of hosted environments may include an Android™ Emulator and a MICROSOFT® WINDOWS® Virtual Machine.

Implementing a server-side architecture that includes each application and hosted environment in a container, and that includes a virtualization module and/or an operating system may provide security among different applications (e.g., non-native applications) executing in the server-side hosted environment. The architecture allows one application (e.g., application 314 a) to be isolated from another application (e.g., application 314 n). Such isolated, containerized execution of an application may provide increased security and performance guarantees by isolating execution to dedicated hardware. The hardware and software runtime may be standardized such that application performance may be consistent regardless of which server or which server hardware runs the individual runtime instance. The hardware and software runtime may therefore provide virtualization at scale.

In some implementations, a cloud application platform may dynamically create, allocate, and/or provision a container and/or a hosted environment on an as-needed basis. For example, when a user initializes an application (e.g., initiates execution of an application in the cloud), a cloud application platform may create an instance of a container and/or a hosted environment to run application. In addition, once the user completes operating the application, the cloud application platform may then delete the instance of the container and/or the hosted environment. Referring to FIGS. 2 and 3, a user interacting with an input device and a computing device may initiate execution of the application 314 a. For example, the computing device may provide an input data stream to the cloud application platform 202 by way of the network 104. In response, the cloud application platform 202 may create the instance of the container 310 a for executing the application 314 a in the hosted environment 312 a. The server 350 may output a video and/or audio stream of data (e.g., output content by way of an edge node and the network 104) to the computing device of the user for consumption by the user. The user interacting with the input device and the computing device may then initiate stopping the execution of the application 314 a. For example, the computing device may provide an input data stream to the cloud application platform 202 by way of the network 104. In response, the cloud application platform 202 may stop execution of the application 314 a in the container 310 a and then may delete the instance of the container 310 a.

FIG. 4 is an illustration of an exemplary architecture of a system 400 for providing web real-time communication between a computing device and a cloud application platform included a server-side environment. For example, referring to FIG. 2, a computing device 406 may be a computing device included in the computing devices 206. The computing device 406 may communicate and interface with the cloud application platform 202 by way of the network 104. As described with reference to FIG. 2, the computing device 406 may provide an input data stream 410 to the cloud application platform 202. The computing device 406 may receive a video/audio output data stream 412 from the cloud application platform 202 by way of the network 104.

A computing device may include a streaming technology stack. A cloud application platform may include a streaming technology stack. A streaming technology stack may implement the streaming of data between a computing device and a cloud application platform (e.g., a server included in the cloud application platform). For example, referring to FIG. 2, the system 200 may include the system 400. The system 400 may provide web-based (Internet based) real-time, direct, and uninterrupted communication between the computing device 406 and the cloud application platform 202 that applies to both the input data stream 410 and the video/audio output data stream 412.

In some implementations, a streaming technology stack may be implemented using a web real-time communication protocol stack (e.g., a WebRTC protocol stack). The use of a WebRTC protocol stack may enable low latency communications between a sender of streaming data and a receiver of the streaming data. Such low latency communications may enable live streaming between computing systems.

For example, a user may interact with the computing device 406 when interfacing with an application executing in the cloud application platform 202. The user may view, listen to, and/or otherwise interact with content provided by the cloud application platform 202 that may be presented on a display device 422 included in the computing device 406 and/or played on one or more speakers 424 included in the computing device 406. For example, the cloud application platform 202 may provide, send, or transmit the video/audio output data stream 412 using a streaming technology stack 418 that implements a web real-time communication protocol stack 420. The computing device 406 may receive the content from the cloud application platform 202 in a web browser or other application executing locally on the computing device 406. For example, the computing device 406 may include a streaming technology stack 414 that implements a web real-time communication protocol stack 420 that receives the video/audio output data stream 412 from the cloud application platform 202 in real-time. The streaming technology stack 414 may also provide the input data stream 410 from the computing device 406 to the cloud application platform 202 for use or processing by the streaming technology stack 418. Such communications between the computing device 406 and the cloud application platform 202, and specifically between the streaming technology stack 414 and the streaming technology stack 418, may provide direct and uninterrupted communications between the cloud application platform 202 and the computing device 406. The direct and uninterrupted communications may allow for real-time interactions between the computing device 406 and the application running on the cloud application platform 202. Real-time interactions with a cloud-hosted application may be especially critical when the cloud-based application is a game.

A web real-time communication protocol stack may be used to provide data (e.g., digital data, audio data, video data, etc.) between computing systems and computing devices (e.g., the computing device 406 and the cloud application platform 202). The ability to transmit and/or receive such data in real-time may provide support for richer user experiences when interacting with a cloud-hosted application. For example, the user experiences may include, but are not limited to, in-app advertising (IAA), in-app purchases (IAP), and social features such as sharing and requests (e.g., game requests). The system 200, when incorporating the system 400, may allow generic streaming applications to live in the cloud and be accessible to client computing devices of users. The system 200 may provide real-time communications and interactions between a computing device and a cloud application platform without the need for any additional installation or setup for the streaming application.

FIG. 5 is an illustration of an exemplary architecture of a system 500 for hosting an application in a server-side environment that shows the details of implementing exemplary architecture in data centers that provide the server-side environment. For example, the system 500 may include a data center 510. In some implementations, a cloud application platform may interface with a data center. For example, referring to FIG. 2, the cloud application platform 202 may interface with the data center 510.

In some implementations, a data center may interface with one or more servers and other equipment that may be located in a particular location, space, or area and that are directly connect to an Internet network backbone. Such a location, space, or area may be referred to as a colocation center. For example, the data center 510 may interface with one or more colocation centers such as the cloud hosting edges 512 a-b. Each cloud hosting edge 512 a-b may be a location or space for server(s) and equipment that virtualize and/or emulate an operating system environment for executing non-native applications in the cloud. For example, the server 350 may be an example of a server included in a cloud hosting edge. In one non-limiting example, the cloud hosting edge 512 a may be a colocation center that includes servers and equipment for supporting non-native applications intended to run in a first operating system (e.g., a MICROSOFT® WINDOWS® operating system). The cloud hosting edge 512 b may be a colocation center that includes servers and equipment for supporting non-native applications intended to run in a second operating system (e.g., an Android™ operating system). Though the data center 510 shown in FIG. 5 interfaces with two cloud hosting edges, in some implementations, a data center may interface with one cloud hosting edge, and in some implementations, a data center may interface with multiple cloud hosting edges (e.g., two cloud hosting edges, more than two cloud hosting edges). In some implementations, the data center 510 may interface with at least one cloud hosting edge for supporting a virtualization of an operating system. In some implementations, the data center 510 may interface with at least one cloud hosting edge for supporting emulation of an operating system.

In some implementations, a data center may interface with one or more edge servers. In these cases, the servers may perform computing, networking, storage, security, and other computer-based functions and interactions by way of edge nodes. For example, referring to FIG. 2, the cloud application platform 202 may utilize edge computing to efficiently receive an input data stream and to efficiently serve content using an output video and/or audio data stream. Each of the servers 228 a-c may be a cloud edge OS as shown in the example of FIG. 5. Referring to FIG. 3, the server 350 may represent a cloud edge OS as shown in FIG. 5.

Each cloud hosting edge may include at least one cloud edge operating system (OS). For example, a cloud edge OS may be an edge server in a cloud hosting edge. For example, referring to FIG. 3, the server 350 may be a cloud edge OS. For example, the cloud hosting edge 512 a may include cloud edge OSs 514 a-b. The cloud hosting edge 512 b may include cloud edge OSs a-b. Though each of the cloud hosting edges 512 a-b shown in FIG. 5 include two cloud edge OSs, in some implementations, a cloud hosting edge may include one cloud edge OS, and in some implementations, a cloud hosting edge may include multiple cloud edge OSs (e.g., two cloud edge OSs, more than two cloud edge OSs). In some implementations, each cloud hosting edge may include the same number of cloud edge OSs. In some implementations, each cloud hosting edge may include a different number of cloud edge OSs.

A cloud edge OS may include one or more containers for virtualizing an operating system. Each container may execute a non-native application intended to run in an operating system in a virtualized environment provided by the container. Each container may include hardware and/or software for virtualizing an execution environment for a non-native application intended to run in the execution environment. For example, the cloud edge OS 514 a may include containers 518 a-b. The cloud edge OS 514 b may include containers 522 a-b. Each container 518 a-b may include a machine emulator module 520 a-b, respectively. Each container 522 a-b may include a machine emulator module 524 a-b, respectively.

Each machine emulator module 520 a-b and 524 a-b may include hardware and/or software for virtualizing an execution environment (e.g., a MICROSOFT® WINDOWS® operating system environment) for a non-native application intended to run in the execution environment (e.g., for a non-native application intended to run in a MICROSOFT® WINDOWS® operating system environment). In cases where a non-native application is a gaming application, a machine emulator module (e.g., machine emulator modules 520 a-b, machine emulator modules 524 a-b) may run the operating system that the non-native gaming application was intended to run on in order to execute the gaming application during a game session.

A cloud edge OS may include one or more containers for emulating an operating system. Each container may execute a non-native application intended to run in an operating system in an emulated environment provided by the container. Each container may include hardware and/or software for emulating an execution environment for a non-native application intended to run in the execution environment. For example, the cloud edge OS 516 a may include containers 526 a-b. The cloud edge OS 516 b may include containers 530 a-b. Each container 526 a-b may include a machine emulator module 528 a-b, respectively. Each container 530 a-b may include a machine emulator module 532 a-b, respectively.

A machine emulator module may include hardware and/or software for emulating and/or virtualizing an execution environment for a non-native application intended to run in the execution environment. A machine emulator module may be a generic open-source machine emulator and virtualizer that may run an operating system (e.g., the execution environment) for a gaming application executing during a game session. For example, each machine emulator module 528 a-b and 532 a-b may include hardware and/or software for emulating an execution environment (e.g., an Android™ operating system environment) for a non-native application intended to run in the execution environment (e.g., for a non-native application intended to run in an Android™ operating system environment). In cases where a non-native application is a gaming application, a machine emulator module (e.g., machine emulator modules 528 a-b, machine emulator modules 532 a-b) may run the operating system that the non-native gaming application was intended to run on in order to execute the gaming application during a game session.

Though each of the cloud edge OSs 514 a-b and 516 a-b shown in FIG. 5 include two containers, in some implementations, a cloud edge OS may include one container, and in some implementations, a cloud edge OS may include multiple containers (e.g., two containers, more than two containers). In some implementations, each cloud edge OS may include the same number of containers. In some implementations, each cloud edge OS may include a different number of containers.

A computing device may run a browser application locally on the computing device. A user may interact with the browser application by way of an internet connection to a web service to access a cloud server management service. The we service may process a request to execute the non-native application in the cloud application platform. In some implementations, the web service may interface with one or more edge nodes in an edge computing environment. Through the browser application a user may interact with a non-native application executing in a cloud application platform that hosts the non-native application. In some implementations, a product edge may provide an interface point between communicating entities such as a computing device and one or more servers. The product edge may include one or more of computers, routers, switches, multiplexers, and/or other types of network interface equipment, hardware, and/or software for implementing and managing the communication interface point.

A computing device may run a social media application locally on the computing device. In some implementations, the user may run the social media application by using the browser. A user may interact with the social media application by way of an internet connection to a web service to access a cloud server management service. In some implementations, the social media application may provide real-time game play (e.g., real-time access and interactions with a gaming application) to a user (an end user) of the computing device. In some implementations, the browser application may provide real-time game play (e.g., real-time access and interactions with a gaming application) to a user (an end user) of the computing device.

A computing device may execute a browser application. Referring to FIGS. 4 and 5, the computing device 406 may execute a browser application 534. A user may interact with the browser application 534. A user interacting with the browser application 534 may input a web page address for a web page that may serve the content for the page. The web page address may be for a cloud application platform that may execute non-native applications. The web page address may be provided to an internet connection 536 using Hypertext Transfer Protocol (HTTP) or Hypertext Transfer Protocol Secure (HTTPS) for data communication with a cloud server management service 546. For example, the browser application 534 may provide game play to the user of the computing device by allowing the user to access and interact with a gaming application (e.g., a video game) that may be executed in the cloud application platform.

A computing device may execute a social media application. Referring to FIGS. 4 and 5, the computing device 406 may execute a social media application 548. A user may interact with the social media application 548. The social media application 548 may provide game play to the user of the computing device by allowing the user to access and interact with a gaming application (e.g., a video game) that may be executed in the cloud application platform.

A web service may receive requests to access web pages using a cloud server management service. For example, web service 544 in the data center 510 may receive a web page address for a cloud gaming application that the web service provides to a cloud server management service 546. The cloud server management service 546 may provide access to the non-native application executing in a cloud application platform by way of the browser application 534.

A product edge may provide an interface point between communicating entities. For example, a product edge 538 may provide a communication interface point for the computing device 406 and each cloud edge OS included in cloud hosting edge 512 a and cloud hosting edge 512 b. For example, the product edge 538 may direct or route input received from the computing device 406 to the web service 544. Referring to FIG. 4, the product edge 538 may receive the data from the computing device 406 using the input data stream 410 by way of the internet connection 536 as provided by the network 104. The product edge 538 may direct or route input received from the computing device 506 to a container executing a non-native application. The product edge 538 may direct or route output data (e.g., the video/audio output data stream 412 as shown in FIG. 4) from a container executing a non-native application to the computing device 406 using an internet connection 540 provided by the network 104. For example, the internet connection 540 may provide a communication channel for sending and receiving real-time streaming video and/or audio data between the computing device 406 and a container on a cloud edge OS using a streaming technology stack that implements a web real-time communication protocol stack. In some implementations, each cloud hosting edge may include a product edge. The product edge may include one or more of servers, routers, switches, multiplexers, and/or other types of network interface equipment, hardware, and/or software for implementing and managing the communication interface point. In some implementations, the network 104 may provide the internet connection 536 and the internet connection 540.

A proxy server 542 may provide information and data to the internet connection 540 through a firewall. The proxy server 542 may be an application that acts as an intermediary between application requests and the cloud server management service 546. For example, in cases where a game session is executing in the machine emulator module 520 a, the proxy server 542 may be an application that acts as an intermediary between the game session online requests and the cloud server management service 546. In some implementations, the proxy server 542 may be a forward proxy that may provide requests, information, and/or data from the cloud hosting edge 512 a and/or the cloud hosting edge 512 b to the computing device 406 by way of the internet connection 540 through a firewall.

FIG. 6 is an illustration of an exemplary architecture of a system 600 for hosting an application intended to execute in a first operating system in a server-side environment. The first operating system may be a desktop operating system. For example, the first operating system may be a MICROSOFT® WINDOWS® operating system. The system 600 may host an application intended to execute in a MICROSOFT® WINDOWS® operating system. The system 600 may host the application in a server-side hosted environment as shown in, for example, FIG. 5. The server-side hosted environment may be non-native to the application. The server-side hosted environment may include a virtual machine (e.g., machine emulator module 520 a) for virtualizing the environment in the server intended to run the application.

A user interacting with a browser application on a computing device may enter a web page address for a cloud application platform. Referring to FIG. 5, a user of the computing device 406 may enter a web page address to access a cloud application platform executing the non-native application that the user wants to interact with. The product edge 538 may direct the web page address received by way of the internet connection 536 using product edge service 612 and network load balancer (NLB) 614 to the cloud server management service 546 of the web service 544. The cloud server management service 546 may manage access to a container that is implementing a virtualization of the execution environment for the non-native application in the cloud application platform.

In some implementations, the cloud server management service 546 may be a cloud gaming load balancer that distributes one or more games sessions over a set of operating system hosts. For example, cloud server management service 546 may assign a game session to the container 518 a of the cloud edge OS 514 a. The cloud server management service 546 may balance the distribution of the one or more game sessions over the set of operating system hosts with the intention of making the overall processing of each game session as efficient as possible.

A web service may access a container that may execute a non-native application on a cloud edge OS. For example, the web service 544 may communicate with the container 518 a that may execute the non-native application in a virtualization of the first operating system. The cloud server management service 546 may communicate with a data control module (e.g., host manager module 616) included in the container 518 a. The host manager module 616 may interface with a configuration and deployment management platform module (e.g., emulator manager module 618).

The emulator manager module 618 may provide a kernel-based virtual machine (KVM) access to a Quick EMUlator (QEMU) hosted virtual machine that performs the hardware virtualization in the machine emulator module 520 a in the container 518 a. The machine emulator module 520 a may be a generic, open-source machine emulator and/or virtualizer used for running an operating system when an application (e.g., application 620) is executing during a session. For example, in cases where the application is a gaming application, a machine emulator module may run the operating system when a gaming application is executing during a gaming session.

The emulator manager module 618 may manage one or more virtual machines (e.g., the machine emulator module 520 a) running inside of a container (e.g., the container 518 a). The host manager module 616 may also communicate with a virtual machine (VM) manager module 626 that manages the machine emulator module 520 a. The host manager module 616 may manage one or more containers (e.g., the container 518 a) running inside of an operating system host (e.g., cloud edge OS 514 a). In some implementations, a software suite may be used by an operating system running native to the cloud edge OS 514 a to spawn the machine emulator module 520 a.

A machine emulator module may virtualize or emulate hardware and/or an operating system for execution of a non-native application in a cloud application platform. For example, the machine emulator module 520 a may virtualize or emulate the hardware and/or operating system for execution of the non-native application (e.g., the application 620) in a sandboxed environment included in an application container 624 in the machine emulator module 520 a. The application 620 may execute in the machine emulator module 520 a of the cloud edge OS 514 a in such a way that a user may interact with the application 620 as if the application 620 were executing locally on the computing device 406. For example, in cases where the application is a gaming application (e.g., a game), the machine emulator module may run the operating system when a gaming application is executing during a gaming session.

An application container may provide a restrictive secure environment for executing an application in a cloud application platform. The secure environment may provide the security needed to execute the application in the cloud. For example, the application container 624 may provide a restrictive process execution environment for the application 620. In cases where a game session is executing in the machine emulator module 520 a, the restrictive process execution environment may provide additional resource security and isolation for the game session as it is executing in the machine emulator module 520 a.

The machine emulator module 520 a may include a logging service 628, an application session manager module 630, an application container partial application session 632, and a partial application session 636 that includes a cloud layer 634. The logging service 628 may record information and data regarding details about the application 620 executing in the machine emulator module 520 a that may be provided to a logging service module 638 included in the web service 544.

A logging service may collect and aggregate log messages for storage in a database for further analysis. For example, the cloud server management service 546 may assign a game session to the container 518 a. The logging service 628 may collect and aggregate log messages from the game session executing in the machine emulator module 520 a. The logging service 628 may store the log messages in a repository or database for later analysis.

A distributed messaging system module may store information and data for possible access by a user. For example, the logging service module 638 may receive information and data regarding details about the application 620 executing in the machine emulator module 520 a from the logging service 628. The logging service module 638 may provide a distributed messaging system to the web service 544 for collecting, aggregating, and/or delivering high volumes of message data with low latency to a user.

An application session manager module may manage and/or control the operation of a virtual machine. For example, the application session manager module 630 may control the operation of the machine emulator module 520 a. The application session manager module 630 may communicate or interface with the cloud server management service 546 and a Graph application programming interface (API) 640. The application session manager module 630 may prepare a virtual machine (e.g., the machine emulator module 520 a) for running an application (e.g., the application 620) in the cloud. In a non-limiting example, the application session manager module 630 may prepare the machine emulator module 520 a for running the application 620 by installing the application binaries and/or by downloading one or more user profiles. In addition, or in the alternative, in cases where a game session is executing in the machine emulator module 520 a, the application session manager module 630 may manage the game session.

A Graph API may provide a representation of information and/or data from a social media platform. Referring to FIG. 5, the Graph API 640 may upload information and data related to the execution of the non-native application in the cloud application platform to the browser application 534 running on the computing device 406. For example, the Graph API 640 may be an HTTP-based API that may access a social graph of a social media platform.

The application container partial application session 632 may be a process that runs or executes one or more parts of the application 620 in the application container 624. The selection and/or determination of the one or more parts of the application 620 to run in the application container 624 may be based on the ability of the process to run the one or more parts of the application 620 under the restrictive permissions provided by the application container 624. Executing or running the one or more parts of the application 620 under such restrictive permissions may provide the security necessary to run the application 620 in the cloud edge OS 514 a. In cases where the application 620 is a game and a game session is executing in the machine emulator module 520 a, the game session may be split or divided into one or more sessions that are split in this manner for security reasons.

The partial application session 636 may be a process that creates the application 620 in the application container 624. The partial application session 636 may be a process that captures the real-time streaming video and/or audio data output by the application 620. The partial application session 636 may be a process that injects an input data stream into the real-time streaming video and/or audio data output by the application 620. The partial application session 636 may be a process that communicates with the computing device 406 using WebRTC when providing the real-time streaming video and/or audio data injected with the input data stream to the computing device 406.

The partial application session 636 may provide a video/audio output data stream to the product edge 538 by way of the cloud layer 634. The cloud layer 634 may include a low-level library. The library may handle the communications for the application running on a virtual machine. For example, in cases where a game session is executing in the machine emulator module 520 a, the cloud layer 634 may include a low-level library that handles the communications for the game using WebRTC. The cloud layer 634 may use the low-level library when sending real-time streaming video and/or audio data to the computing device 406. The cloud layer 634 may use the low-level library when receiving real-time streaming video and/or audio data from the computing device 406.

An application container may include a sandbox layer that facilitates the execution of a non-native application, intended to run in an operating system, in an emulated environment for the operating system provided by a container. For example, the container 518 a may provide an application container 624 that includes the application 620. The application 620 may include a sandbox layer 622. The machine emulator module 520 a included in the container 518 a may include hardware and/or software for virtualizing an execution environment (e.g., a MICROSOFT® WINDOWS® operating system environment) for the non-native application intended to run in the execution environment (e.g., for a non-native application intended to run in a MICROSOFT® WINDOWS® operating system environment).

The sandbox layer 622 may facilitate the execution of the application 620 in the application container 624. The sandbox layer 622 may be a compatibility layer that intercepts one or more calls made by the application 620 to an application programming interface (API) of the operating system that the application 620 was intended to run in. The sandbox layer 622 may transparently modify the intercepted one or more application calls so that the one or more application calls function in the container 518 a. The modifying of the intercepted one or more application calls by the sandbox layer 622 avoids the need to modify the application 620 (e.g., modify the original application binary file) in order for the application 620 to function in the cloud edge OS 514 a.

In some implementations, an output of the sandbox layer 622 of the application 620 may connect to or interface with a domain name system (DNS) 644 included in the product edge 538. The DNS 644 may resolve network addresses from domain names. In some cases, the video/audio output data stream may be sent from the cloud layer 634 to the NLB 614 using the WebRTC protocol. In some cases, the application 620 may access the internet connection 540 using the proxy server 542 by way of the sandbox layer 622.

FIG. 7 is an illustration of an exemplary architecture of a system 700 for hosting an application intended to execute in a second operating system in a server-side environment. For example, the second operating system may be an Android™ operating system. The system 700 may host an application intended to execute in an Android™ operating system. The system 700 may host the application in a server-side environment as shown in, for example, FIG. 5. The server-side environment may be non-native to the application.

A user interacting with a browser application on a computing device may enter a web page address for a cloud application platform. Referring to FIG. 5, a user of the computing device 406 may enter a web page address to access a cloud application platform executing the non-native application that the user wants to interact with. The Product edge 538 may direct the web page address received by way of the internet connection 536 using the product edge service 612 and the network load balancer (NLB) 614 to the cloud server management service 546 of the web service 544. The cloud server management service 546 may manage access to a container that is implementing a virtualization of the execution environment for the non-native application in the cloud application platform.

In some implementations, the cloud server management service 546 may be a cloud gaming load balancer that distributes one or more games sessions over a set of operating system hosts. For example, the cloud server management service 546 may assign a game session to the container 526 a of the cloud edge OS 516 a. The cloud server management service 546 may balance the distribution of the one or more game sessions over the set of operating system hosts with the intention of making the overall processing of each game session as efficient as possible.

A web service may access a container that may execute a non-native application on an edge host. For example, the web service 544 may communicate with the container 526 a that may execute the non-native application in a virtualization of the second operating system. The web service 544 may communicate with the container 526 a using an application session manager module 710. The cloud server management service 546 may communicate or interface with the application session manager module 710.

An application session manager module may manage a session of an application running in a container. For example, the application session manager module 710 may manage a session of an application 720 running in the container 526 a. In cases where the application is a gaming application, the application session manager module 710 may manage the game session executing in the container 526 a. The application session manager module 710 may manage one or more input events received from the computing device 406. The application session manager module 710 may make a remote procedure call (RPC) to the machine emulator module 528 a. In some implementations, the RPC may be provided to the machine emulator module 528 a using an operating system debug bridge input. For example, in implementations where the second operating system is an Android™ operating system, the RPC may be an Android debug bridge (ADB) input. For example, an ADB may be a communication channel that sends commands to the emulated Android™ operating system.

The application session manager module 710 may also communicate or interface with media processor module 712. The media processor module 712 may provide a platform in the container 526 a for communications between the application session manager module 710, the machine emulator module 528 a, and the NLB 614 of the product edge 538. The product edge 538 may provide streaming video/audio content in real-time using a web real-time communication protocol stack (e.g., a WebRTC protocol stack) for securely providing and/or receiving streaming video/audio content. The media processor module 712, using a WebRTC protocol stack to communicate with the computing device 406, may provide the streaming video/audio content to the computing device 406 in real-time. The media processor module 712 may extract one or more frames from the streaming video/audio content provided by the machine emulator module 528 a to assist the application session manager module 710 with the providing of the streaming video/audio content to the computing device 406.

In some implementations, a software suite may be used by an operating system running native to the cloud edge OS 516 a to spawn the machine emulator module 528 a. The machine emulator module 528 a may virtualize or emulate the hardware and operating system for execution of the non-native application (e.g., the application 720).

An application executing in the cloud may include an integrated software development kit that provides an application with cloud features. For example, software development kit (SDK) 714 may be a software library of functions that are integrated into the application 720. The SDK 714 may add cloud features to the application 720 that allow the application 720 to execute in the cloud edge OS 516 a and that allow a user interacting with the computing device 406 to provide input to and/or receive output from the application 720.

The machine emulator module 528 a may include an application emulator proxy 716. The application 720 may interface with an instance of an operating system (e.g., OS 718) that is running in the machine emulator module 528 a. The application emulator proxy 716 may interface or communicate with the OS 718 using operating system (OS) broadcasts. The application emulator proxy 716 may receive requests from the SDK 714 via operating system (OS) broadcasts from the SDK 714. The application emulator proxy 716 may also send responses to the SDK 714 using OS broadcasts.

The application 720 may establish one or more socket connections to local proxy client 722. The local proxy client 722 may provide information and data output by the application 720 for input to the proxy server 542. For example, the local proxy client 722 may transparently provide internet access to the application 720 by way of the proxy server 542.

A machine emulator module may virtualize or emulate hardware and/or an operating system for execution of a non-native application in a cloud application platform. For example, the machine emulator module 528 a may virtualize or emulate the hardware and/or operating system for execution of the non-native application (e.g., the application 720) in the machine emulator module 528 a. The application 720 may execute in the machine emulator module 528 a of the cloud edge OS 516 a in such a way that a user may interact with the application 720 as if the application 720 were executing locally on the computing device 406. For example, in cases where the application is a gaming application (e.g., a game), the machine emulator module 528 a may run the operating system when a gaming application is executing during a gaming session.

An application container may provide a restrictive secure environment for executing an application in a cloud application platform. The secure environment may provide the security needed to execute the application in the cloud. For example, the machine emulator module 528 a may provide a restrictive process execution environment for the application 720. In cases where a game session is executing in the machine emulator module 528 a, the restrictive process execution environment may provide additional resource security and isolation for the game session as it is executing in the machine emulator module 528 a.

The application 720 may use the local proxy client 722 for bidiectional communications between the application 720 and the proxy server 542. For example, the application 720 may use the local proxy client 722 to send information to and/or to receive information from the Internet by way of the internet connection 540 using the proxy server 542 as a communication proxy. The proxy server 542 may be an application that acts as an intermediary between application requests and the cloud server management service 546. For example, in cases where a game session is executing in the machine emulator module 528 a, the proxy server 542 may be an application that acts as an intermediary between the game session online requests and the cloud server management service 546. In some implementations, the proxy server 542 may be a forward proxy that may provide requests, information, and/or data from the cloud hosting edge 512 a and/or the cloud hosting edge 512 b to the computing device 406 by way of the internet connection 540 through a firewall.

The application session manager module 710 may provide information and data received from the media processor module 712 to the logging service module 638 included in the web service 544. The information and data may be about the execution of the application 720 in the machine emulator module 528 a. The logging service module 638 may store and provide the information and data for possible access by a user. For example, the logging service module 638 may receive information and data regarding details about the application 720 executing in the machine emulator module 528 a from the application session manager module 710. The logging service module 638 may provide a logging service to the cloud server management service 546 for collecting, aggregating, and/or delivering high volumes of message data with low latency to a user.

The application session manager module 710 may provide information and data received from the media processor module 712 to the Graph API 64 included in the web service 544. Referring to FIG. 5, the Graph API 640 may upload information and data related to the execution of the non-native application (e.g., the application 720) in the container 526 a to the browser application 534 running on the computing device 406. For example, the Graph API 640 may be an HTTP-based API that may access a social graph of a social media platform.

An output of the machine emulator module 528 a may connect to or interface with the domain name system (DNS) 644 included in the product edge 538. The DNS 644 may resolve network addresses for domain names to facilitate the communications between the container 526 a and the computing device 406 by way of the internet connection 540.

As indicated in FIG. 6 and FIG. 7, information and data passed between, within, or provided to components of the containers 518 a and 526 a, the web service 544, and the product edge 538 may be in the format and/or utilize of one of a SOCKS internet protocol, a user datagram protocol (UDP), a transmission control protocol (TCP), a named pipe connection, a streamed pipe connection, an https protocol, a Thrift software framework, or a secure real-time transport protocol (SRTP)+stream control transmission protocol (SCTP) data transport layer security (DTLS) intrusion countermeasures electronics (ICE) framework. Referring to FIG. 6, the SRTP+SCTP DTLS ICE framework may establish and utilize a connection between the cloud edge OS 516 a, and in particular the machine emulator module 520 a, and the computing device 406 for use with a web real-time communication protocol stack (e.g., a WebRTC protocol stack) for securely providing and/or receiving streaming video/audio content. Referring to FIG. 7, the SRTP+SCTP DTLS ICE framework may establish and utilize a connection between the cloud edge OS 516 a, and in particular the container 526 a, and the computing device 406 for use with a web real-time communication protocol stack (e.g., a WebRTC protocol stack) for securely providing and/or receiving streaming video/audio content.

The Thrift software framework may provide a software framework for exchanging information and data between computing devices using a software stack with a code generation engine to build services that work across various application programming languages. The UDP protocol may be used for sending messages between modules. The TCP protocol may be used to provide a stream of bytes between modules. A named pipe connection may provide a logical connection between modules for use in interprocess communications. A streamed pipe connection may provide a connection between modules that allows for a distributed transaction between the modules. A SOCKS internet protocol facilitates the exchange of network packets through a proxy server (e.g., the proxy server 542).

FIG. 8 is a flow diagram of an exemplary computer-implemented method 800 for hosting a non-native application in a server-side hosted environment. In some implementations, the server-side hosted environment may be for a cloud gaming system. The steps shown in FIG. 8 may be performed by any suitable computer-executable code and/or computing system, including the system(s) illustrated in FIGS. 1, 2, and 4-7. In one example, each of the steps shown in FIG. 8 may represent an algorithm whose structure includes and/or is represented by multiple sub-steps, examples of which will be provided in greater detail below.

As illustrated in FIG. 8, at step 810 one or more of the systems described herein may execute, by a server-side hosted environment, a first application non-native to the server-side hosted environment. The executing may include virtualizing hardware for the server-side hosted environment that supports the execution of the first application in the server-side hosted environment. For example, a cloud edge OS may include a container that includes hardware virtualization for virtualizing hardware for a server-side hosted environment provided by the cloud edge OS that is included in a cloud hosting edge. For example, a cloud edge OS may include a container that includes an emulator for virtualizing hardware for a server-side hosted environment provided by the cloud edge OS that is included in a cloud hosting edge.

In some embodiments, the term “server-side hosted environment” may refer to a cloud-hosted infrastructure environment that is architected to include at least one remote server, an execution environment, and hardware for implementing and running a cloud-hosted system for hosting an application non-native to the execution environment of the cloud-hosted infrastructure. Examples of a server-side hosted environment may include, without limitation, a data center, and/or one or more locations, spaces, or areas where one or more servers and other equipment may directly connect to an Internet network backbone (e.g., one or more colocation centers). For example, a colocation center may be a location, space, or area for server(s) and equipment that virtualize and/or emulate an operating system environment for executing non-native applications in the cloud.

In some embodiments, the term “virtualizing” may refer to running or executing a virtual instance of a computer system (e.g., computer hardware and/or software) in a container that may be abstracted from the actual hardware of the host computing system. Examples of virtualizing may include, without limitation, creating one or more containers in a cloud edge OS for virtualizing hardware in the cloud edge OS for executing an application non-native to the computing environment of the cloud edge OS.

The systems described herein may perform step 810 in a variety of ways. In one example, referring to FIG. 5, the cloud edge OS 514 a may include containers 518 a-b that include machine emulator modules 520 a-b, respectively, for virtualizing hardware for a server-side hosted environment provided by the cloud edge OS 514 a included in the cloud hosting edge 512 a. The cloud edge OS 514 b may include containers 522 a-b that include machine emulator modules 524 a-b, respectively, for virtualizing hardware for a server-side hosted environment provided by the cloud edge OS 514 a included in the cloud hosting edge 512 a.

As illustrated in FIG. 8, at step 820 one or more of the systems described herein may receive, by the server-side hosted environment by way of a network, an input data stream from a second application executing on a computing device. For example, the hardware virtualization may receive an input data stream from a web browser application running on a computing device.

In some embodiments, the term “input data stream” may refer to a stream of information and data for controlling the execution of a non-native application hosted in the server-side hosted environment of a cloud application platform. Examples of an input data stream may include, without limitation, a sequence of elements used to represent data elements that may be received over time.

The systems described herein may perform step 820 in a variety of ways. In one example, the container 518 a may receive an input data stream 410 from the browser application 534 by way of the internet connection 536 provided by the network 104 to the product edge service 612 included in the product edge 538. The product edge service 612 may provide the input data stream 410 to the NLB 614 which in turn provides the input data stream 410 to the cloud server management service 546.

As illustrated in FIG. 8, at step 830 one or more of the systems described herein may process, by the server-side hosted environment and by the first application while executing in the virtualized hardware, the input data stream, the processing generating an output data stream. For example, a virtual machine that virtualizes the hardware may execute a non-native application that may process the input data stream to generate an output data stream.

In some embodiments, the term “output data stream” may refer to a stream of information and data (e.g., streaming video and/or audio data) output by an application that, in some cases, is responsive to received input data. Examples of an output data stream may include, without limitation, streaming media, log files, ecommerce purchases, in-game player activity (e.g., interactions with a gaming application), information from social networks, and geospatial services.

The systems described herein may perform step 830 in a variety of ways. In one example, the application 620 executing in the application container 624 may process the input data stream received by the application container 624 from the application session manager module 630 to generate an output data stream.

As illustrated in FIG. 8, at step 840 one or more of the systems described herein may output, by the server-side hosted environment and to the computing device by way of the network, the output data stream for use by the second application. For example, the hardware virtualization may output the output data stream in real-time by way of a network to a browser running in a computing device.

The systems described herein may perform step 840 in a variety of ways. In one example, the cloud layer 634 may output the output data stream in real-time to the NLB 614 included in the product edge 538. The NLB 614 may communicate or interface with the internet connection 540 provided by the network 104 to provide the output data stream in real-time to the computing device 406 for display of the video data on the display device 422 and/or for playing of the audio data by the speakers 424. The real-time communications are implemented by a streaming technology stack that uses a WebRTC protocol stack in each of the computing device 406 and the cloud application platform 202. The use of a WebRTC protocol stack may enable low latency communications between the cloud edge OS 514 a that is sending the streaming data and the computing device 406 that receives the streaming data. Such low latency communications may enable live streaming between the computing device 406 and the cloud edge OS 514 a.

The systems and methods described herein may include various optimizations for a cloud application platform. The optimizations may advantageously improve the functioning of a computer itself by, for example, more efficiently utilizing server-side computing resources, improving a network communication scheme involving virtualization, and reducing network latency for cloud computing. The systems and methods described herein may also improve the fields of virtualization, cloud and/or edge computing, and/or streaming.

Example Embodiments

Example 1: A computer-implemented method for may include executing, by a server-side hosted environment, a first application non-native to the server-side hosted environment, the executing comprising virtualizing hardware for the server-side hosted environment that supports the execution of the first application in the server-side hosted environment, receiving, by the server-side hosted environment by way of a network, an input data stream from a second application executing on a computing device, processing, by the server-side hosted environment and by the first application while executing in the virtualized hardware, the input data stream, the processing generating an output data stream, and outputting, by the server-side hosted environment and to the computing device by way of the network, the output data stream for use by the second application.

Example 2: The computer-implemented method of Example 1, where the first application may include a video game.

Example 3: The computer-implemented method of Example 2, where the second application may include a social media application that provides game play to an end user of the computing device.

Example 4: The computer-implemented method of Example 2, where the second application may include a browser application that provides game play to an end user of the computing device.

Example 5: The computer-implemented method of any of Examples 1-4, where a Web Real-Time Communication protocol stack may be used to transfer data streams between the computing device and the server-side hosted environment.

Example 6: The computer-implemented method of any of Examples 1-5, where the server-side hosted environment may include one of a mobile device OS emulator, or an OS virtual machine.

Example 7: The computer-implemented method of Example 6, where the mobile device OS emulator may be an ANDROID™ OS emulator.

Example 8: The computer-implemented method of Example 6, where the virtual OS machine may be a MICROSOFT® WINDOWS® virtual machine.

Example 9: The computer-implemented method of any of Examples 1-8, where the server-side hosted environment may include a cloud platform that incorporates edge computing.

Example 10: The computer-implemented method of any of Examples 1-9, where virtualizing hardware for the server-side hosted environment that supports the execution of the first application in the server-side hosted environment may include emulating a native environment suited to operate the first application.

Example 11: The computer-implemented method of any of Examples 1-10, where virtualizing hardware for the server-side hosted environment that supports the execution of the first application in the server-side hosted environment may include providing a virtual container in an operating system virtualization layer, the virtual container including a sandboxed execution environment for the first application by the server-side hosted environment.

Example 12: The computer-implemented method of Example 11, wherein virtualizing hardware for the server-side hosted environment that supports the execution of the first application in the server-side hosted environment may further include dynamically provisioning one or more of the first application or the server-side hosted environment within the virtual container in response to a request to provision the first application.

Example 13: The computer-implemented method of any of Examples 1-12, where the computing device may include an artificial-reality system having a display for displaying the output data stream in the artificial-reality system.

Example 14: A system may include at least one physical processor, and physical memory comprising computer-executable instructions that, when executed by the physical processor, cause the physical processor to execute a first application non-native to a server-side hosted environment, the executing comprising virtualizing hardware for the server-side hosted environment that supports the execution of the first application in the server-side hosted environment, receive, by way of a network, an input data stream from a second application executing on a computing device, process, by the first application while executing in the virtualized hardware, the input data stream, the processing generating an output data stream, and output, to the computing device by way of the network, the output data stream for use by the second application.

Example 15: The system of Example 14, where the first application may include a video game.

Example 16: The system of Example 15, where the second application may include one of a social media application that provides game play to an end user of the computing device or a browser application that provides game play to an end user of the computing device.

Example 17: The system of any of Examples 14-16, where a Web Real-Time Communication protocol stack may be used to transfer data streams between the computing device and the server-side hosted environment.

Example 18: The system of any of Examples 14-17, where the server-side hosted environment may include one of a mobile device OS emulator, or an OS virtual machine.

Example 19: The system of any of Examples 14-18, where the server-side hosted environment may include a cloud platform that incorporates edge computing.

Example 20: A non-transitory computer-readable medium including one or more computer-executable instructions that, when executed by at least one processor of a server-side hosted environment, may cause the server-side hosted environment to execute a first application non-native to a server-side hosted environment, the executing comprising virtualizing hardware for the server-side hosted environment that supports the execution of the first application in the server-side hosted environment, receive, by way of a network, an input data stream from a second application executing on a computing device, process, by the first application while executing in the virtualized hardware, the input data stream, the processing generating an output data stream, and output, to the computing device by way of the network, the output data stream for use by the second application.

FIG. 9 is a block diagram of an example system 900 that includes modules for use in a server-side hosted environment for a cloud gaming system. Modules 910 may include the virtualization module 308, the OS 302, one or more containers 310 a-n, and the streaming technology stack 418. Although illustrated as separate elements, one or more of modules 910 in FIG. 9 may represent portions of a single module or application.

In certain embodiments, one or more of modules 910 in FIG. 9 may represent one or more software applications, operating systems, or programs that, when executed by a computing device, may cause the computing device to perform one or more tasks. As illustrated in FIG. 9, example system 900 may also include one or more memory devices, such as memory 940. Memory 940 generally represents any type or form of volatile or non-volatile storage device or medium capable of storing data and/or computer-readable instructions. In one example, memory 940 may store, load, and/or maintain one or more of modules 910. Examples of memory 940 include, without limitation, Random Access Memory (RAM), Read Only Memory (ROM), flash memory, Hard Disk Drives (HDDs), Solid-State Drives (SSDs), optical disk drives, caches, variations or combinations of one or more of the same, and/or any other suitable storage memory.

As illustrated in FIG. 9, the example system 900 may also include one or more physical processors, such as physical processor 930. Physical processor 930 generally represents any type or form of hardware-implemented processing unit capable of interpreting and/or executing computer-readable instructions. In one example, physical processor 930 may access and/or modify one or more of modules 910 stored in memory 940. Additionally, or alternatively, physical processor 930 may execute one or more of modules 910. Examples of physical processor 930 include, without limitation, microprocessors, microcontrollers, Central Processing Units (CPUs), Field-Programmable Gate Arrays (FPGAs) that implement softcore processors, Application-Specific Integrated Circuits (ASICs), portions of one or more of the same, variations or combinations of one or more of the same, and/or any other suitable physical processor.

As illustrated in FIG. 9, the example system may also include the GPUs 306 a-n and the CPUs 308 a-n. For example, the system 900 may use a graphics processing unit (GPU) for image and graphics processing when implementing a server-side hosted environment for a cloud gaming system. The system 900 may use a central processing unit (CPU) for more general processing tasks when implementing a server-side hosted environment for a cloud gaming system. In some implementations, the physical processor may represent one or more of the CPUs 308 a-n. In some implementations, the physical processor 930 may be included in the system 900 in addition to the CPUs 308 a-n.

As illustrated in FIG. 9, the example system 900 may also include one or more additional elements 920. The additional elements 920 generally represent any type or form of hardware and/or software. In one example, physical processor 930 may access and/or modify one or more of the additional elements 920.

One or more repositories may include the additional elements 920. The one or more repositories may be memory (e.g., the memory 940). The one or more repositories may be databases. In some implementations, the additional elements 920 may be included (part of) the system 900. In some implementations, the additional elements 920 may be external to the system 900 and accessible by the system 900.

The additional elements 920 may include a log message database 950. As described with reference to FIG. 6, the logging service may collect and aggregate log messages for storage in a database (e.g., the log message database 950) for further analysis. For example, in cases where the application 620 is a game, the logging service 628 may collect and aggregate log messages from the game session executing in the machine emulator module 520 a and then may store the log messages in the log message database 950 for later analysis.

FIG. 10 illustrates an exemplary network environment 1000 in which aspects of the present disclosure may be implemented. The network environment 1000 may include one or more computing devices (e.g., computing device 1002 and server 1006) and the network 104. In one example, referring to FIGS. 3 and 4, the server 1006 may the server 350 and the computing device 1002 may be the computing device 406.

In this example, the server 1006 may include the physical processor 930 that may be one or more general-purpose processors that execute software instructions. The server 1006 may include a data storage subsystem that includes the memory 940 which may store software instructions, along with data (e.g., input and/or output data) processed by execution of those instructions. The memory 940 may include modules 910 that may be used to control the operation of the server 1006. The server 1006 may include additional elements 920. In some implementations, all or part of the additional elements 920 may be external to the server 1006 and the computing device 1002 and may be accessible by the server 1006 either directly (a direct connection) or by way of the network 104.

The computing device 1002 may represent a client device or a user device, such a desktop computer, laptop computer, tablet device, smartphone, or other computing device. In some implementations, the computing device 1002 may be part of or included in augmented reality glasses, virtual reality headsets, virtual-reality environments, and/or augmented-reality environments, examples of which are described herein with reference to FIGS. 11-12.

The computing device 1002 may include a physical processor 1030, which may represent a single processor or multiple processors, and one or more memory devices (e.g., memory 1040), which may store instructions (e.g., software applications) and/or data in one or more modules 1010. The modules 1010 may store software instructions, along with data (e.g., input and/or output data) processed by execution of those instructions. The modules 101 may include the browser application 534 and the streaming technology stack 414. The computing device 1002 may include additional elements 1020. The additional elements 1020 may include the display device 422 and the speaker(s) 424.

The computing device 1002 may be communicatively coupled to the input server 1006 through the network 104. The network 104 may be any communication network, such as the Internet, a Wide Area Network (WAN), or a Local Area Network (LAN), and may include various types of communication protocols and physical connections. The server 1006 may communicatively connect to and/or interface with various devices through the network 104. In some embodiments, the network 104 may support communication protocols such as transmission control protocol/Internet protocol (TCP/IP), Internet packet exchange (IPX), systems network architecture (SNA), and/or any other suitable network protocols. In some embodiments, data may be transmitted by the network 104 using a mobile network (such as a mobile telephone network, cellular network, satellite network, or other mobile network), a public switched telephone network (PSTN), wired communication protocols (e.g., Universal Serial Bus (USB), Controller Area Network (CAN)), and/or wireless communication protocols (e.g., wireless LAN (WLAN) technologies implementing the IEEE 802.11 family of standards, Bluetooth, Bluetooth Low Energy, Near Field Communication (NFC), Z-Wave, and ZigBee).

The subject matter disclosed herein may be implemented in a variety of ways, with a variety of computing devices 106. However, certain examples may include an artificial-reality system. For example, as described above, a computing device 106, through which a user interacts with the cloud application platform 102, may be an artificial-reality system. Therefore, the present disclosure will provide a detailed discussion of exemplary artificial-reality systems.

Embodiments of the present disclosure may include or be implemented in conjunction with various types of artificial-reality systems. Artificial reality is a form of reality that has been adjusted in some manner before presentation to a user, which may include, for example, a virtual reality, an augmented reality, a mixed reality, a hybrid reality, or some combination and/or derivative thereof. Artificial-reality content may include completely computer-generated content or computer-generated content combined with captured (e.g., real-world) content. The artificial-reality content may include video, audio, haptic feedback, or some combination thereof, any of which may be presented in a single channel or in multiple channels (such as stereo video that produces a three-dimensional (3D) effect to the viewer). Additionally, in some embodiments, artificial reality may also be associated with applications, products, accessories, services, or some combination thereof, that are used to, for example, create content in an artificial reality and/or are otherwise used in (e.g., to perform activities in) an artificial reality.

Artificial-reality systems may be implemented in a variety of different form factors and configurations. Some artificial-reality systems may be designed to work without near-eye displays (NEDs). Other artificial-reality systems may include an NED that also provides visibility into the real world (such as, e.g., augmented-reality system 1100 in FIG. 11) or that visually immerses a user in an artificial reality (such as, e.g., virtual-reality system 1200 in FIG. 12). While some artificial-reality devices may be self-contained systems, other artificial-reality devices may communicate and/or coordinate with external devices to provide an artificial-reality experience to a user. Examples of such external devices include handheld controllers, mobile devices, desktop computers, devices worn by a user, devices worn by one or more other users, and/or any other suitable external system.

Turning to FIG. 11, augmented-reality system 1100 may include an eyewear device 1102 with a frame 1110 configured to hold a left display device 1115(A) and a right display device 1115(B) in front of a user's eyes. Display devices 1115(A) and 1115(B) may act together or independently to present an image or series of images to a user. While augmented-reality system 1100 includes two displays, embodiments of this disclosure may be implemented in augmented-reality systems with a single NED or more than two NEDs.

In some embodiments, augmented-reality system 1100 may include one or more sensors, such as sensor 1140. Sensor 1140 may generate measurement signals in response to motion of augmented-reality system 1100 and may be located on substantially any portion of frame 1110. Sensor 1140 may represent one or more of a variety of different sensing mechanisms, such as a position sensor, an inertial measurement unit (IMU), a depth camera assembly, a structured light emitter and/or detector, or any combination thereof. In some embodiments, augmented-reality system 1100 may or may not include sensor 1140 or may include more than one sensor. In embodiments in which sensor 1140 includes an IMU, the IMU may generate calibration data based on measurement signals from sensor 1140. Examples of sensor 1140 may include, without limitation, accelerometers, gyroscopes, magnetometers, other suitable types of sensors that detect motion, sensors used for error correction of the IMU, or some combination thereof.

In some examples, augmented-reality system 1100 may also include a microphone array with a plurality of acoustic transducers 1120(A)-1120(J), referred to collectively as acoustic transducers 1120. Acoustic transducers 1120 may represent transducers that detect air pressure variations induced by sound waves. Each acoustic transducer 1120 may be configured to detect sound and convert the detected sound into an electronic format (e.g., an analog or digital format). The microphone array in FIG. 11 may include, for example, ten acoustic transducers: 1120(A) and 1120(B), which may be designed to be placed inside a corresponding ear of the user, acoustic transducers 1120(C), 1120(D), 1120(E), 1120(F), 1120(G), and 1120(H), which may be positioned at various locations on frame 1110, and/or acoustic transducers 1120(1) and 1120(J), which may be positioned on a corresponding neckband 1105.

In some embodiments, one or more of acoustic transducers 1120(A)-(J) may be used as output transducers (e.g., speakers). For example, acoustic transducers 1120(A) and/or 1120(B) may be earbuds or any other suitable type of headphone or speaker.

The configuration of acoustic transducers 1120 of the microphone array may vary. While augmented-reality system 1100 is shown in FIG. 11 as having ten acoustic transducers 1120, the number of acoustic transducers 1120 may be greater or less than ten. In some embodiments, using higher numbers of acoustic transducers 1120 may increase the amount of audio information collected and/or the sensitivity and accuracy of the audio information. In contrast, using a lower number of acoustic transducers 1120 may decrease the computing power required by an associated controller 1150 to process the collected audio information. In addition, the position of each acoustic transducer 1120 of the microphone array may vary. For example, the position of an acoustic transducer 1120 may include a defined position on the user, a defined coordinate on frame 1110, an orientation associated with each acoustic transducer 1120, or some combination thereof.

Acoustic transducers 1120(A) and 1120(B) may be positioned on different parts of the user's ear, such as behind the pinna, behind the tragus, and/or within the auricle or fossa. Or, there may be additional acoustic transducers 1120 on or surrounding the ear in addition to acoustic transducers 1120 inside the ear canal. Having an acoustic transducer 1120 positioned next to an ear canal of a user may enable the microphone array to collect information on how sounds arrive at the ear canal. By positioning at least two of acoustic transducers 1120 on either side of a user's head (e.g., as binaural microphones), augmented-reality device 1100 may simulate binaural hearing and capture a 3D stereo sound field around about a user's head. In some embodiments, acoustic transducers 1120(A) and 1120(B) may be connected to augmented-reality system 1100 via a wired connection 1130, and in other embodiments acoustic transducers 1120(A) and 1120(B) may be connected to augmented-reality system 1100 via a wireless connection (e.g., a BLUETOOTH connection). In still other embodiments, acoustic transducers 1120(A) and 1120(B) may not be used at all in conjunction with augmented-reality system 1100.

Acoustic transducers 1120 on frame 1110 may be positioned in a variety of different ways, including along the length of the temples, across the bridge, above or below display devices 1115(A) and 1115(B), or some combination thereof. Acoustic transducers 1120 may also be oriented such that the microphone array is able to detect sounds in a wide range of directions surrounding the user wearing the augmented-reality system 1100. In some embodiments, an optimization process may be performed during manufacturing of augmented-reality system 1100 to determine relative positioning of each acoustic transducer 1120 in the microphone array.

In some examples, augmented-reality system 1100 may include or be connected to an external device (e.g., a paired device), such as neckband 1105. Neckband 1105 generally represents any type or form of paired device. Thus, the following discussion of neckband 1105 may also apply to various other paired devices, such as charging cases, smart watches, smart phones, wrist bands, other wearable devices, hand-held controllers, tablet computers, laptop computers, other external compute devices, etc.

As shown, neckband 1105 may be coupled to eyewear device 1102 via one or more connectors. The connectors may be wired or wireless and may include electrical and/or non-electrical (e.g., structural) components. In some cases, eyewear device 1102 and neckband 1105 may operate independently without any wired or wireless connection between them. While FIG. 11 illustrates the components of eyewear device 1102 and neckband 1105 in example locations on eyewear device 1102 and neckband 1105, the components may be located elsewhere and/or distributed differently on eyewear device 1102 and/or neckband 1105. In some embodiments, the components of eyewear device 1102 and neckband 1105 may be located on one or more additional peripheral devices paired with eyewear device 1102, neckband 1105, or some combination thereof.

Pairing external devices, such as neckband 1105, with augmented-reality eyewear devices may enable the eyewear devices to achieve the form factor of a pair of glasses while still providing sufficient battery and computation power for expanded capabilities. Some or all of the battery power, computational resources, and/or additional features of augmented-reality system 1100 may be provided by a paired device or shared between a paired device and an eyewear device, thus reducing the weight, heat profile, and form factor of the eyewear device overall while still retaining desired functionality. For example, neckband 1105 may allow components that would otherwise be included on an eyewear device to be included in neckband 1105 since users may tolerate a heavier weight load on their shoulders than they would tolerate on their heads. Neckband 1105 may also have a larger surface area over which to diffuse and disperse heat to the ambient environment. Thus, neckband 1105 may allow for greater battery and computation capacity than might otherwise have been possible on a stand-alone eyewear device. Since weight carried in neckband 1105 may be less invasive to a user than weight carried in eyewear device 1102, a user may tolerate wearing a lighter eyewear device and carrying or wearing the paired device for greater lengths of time than a user would tolerate wearing a heavy standalone eyewear device, thereby enabling users to more fully incorporate artificial-reality environments into their day-to-day activities.

Neckband 1105 may be communicatively coupled with eyewear device 1102 and/or to other devices. These other devices may provide certain functions (e.g., tracking, localizing, depth mapping, processing, storage, etc.) to augmented-reality system 1100. In the embodiment of FIG. 11, neckband 1105 may include two acoustic transducers (e.g., 1120(1) and 1120(J)) that are part of the microphone array (or potentially form their own microphone subarray). Neckband 1105 may also include a controller 1125 and a power source 1135.

Acoustic transducers 1120(1) and 1120(J) of neckband 1105 may be configured to detect sound and convert the detected sound into an electronic format (analog or digital). In the embodiment of FIG. 11, acoustic transducers 1120(1) and 1120(J) may be positioned on neckband 1105, thereby increasing the distance between the neckband acoustic transducers 1120(1) and 1120(J) and other acoustic transducers 1120 positioned on eyewear device 1102. In some cases, increasing the distance between acoustic transducers 1120 of the microphone array may improve the accuracy of beamforming performed via the microphone array. For example, if a sound is detected by acoustic transducers 1120(C) and 1120(D) and the distance between acoustic transducers 1120(C) and 1120(D) is greater than, e.g., the distance between acoustic transducers 1120(D) and 1120(E), the determined source location of the detected sound may be more accurate than if the sound had been detected by acoustic transducers 1120(D) and 1120(E).

Controller 1125 of neckband 1105 may process information generated by the sensors on neckband 1105 and/or augmented-reality system 1100. For example, controller 1125 may process information from the microphone array that describes sounds detected by the microphone array. For each detected sound, controller 1125 may perform a direction-of-arrival (DOA) estimation to estimate a direction from which the detected sound arrived at the microphone array. As the microphone array detects sounds, controller 1125 may populate an audio data set with the information. In embodiments in which augmented-reality system 1100 includes an inertial measurement unit, controller 1125 may compute all inertial and spatial calculations from the IMU located on eyewear device 1102. A connector may convey information between augmented-reality system 1100 and neckband 1105 and between augmented-reality system 1100 and controller 1125. The information may be in the form of optical data, electrical data, wireless data, or any other transmittable data form. Moving the processing of information generated by augmented-reality system 1100 to neckband 1105 may reduce weight and heat in eyewear device 1102, making it more comfortable to the user.

Power source 1135 in neckband 1105 may provide power to eyewear device 1102 and/or to neckband 1105. Power source 1135 may include, without limitation, lithium ion batteries, lithium-polymer batteries, primary lithium batteries, alkaline batteries, or any other form of power storage. In some cases, power source 1135 may be a wired power source. Including power source 1135 on neckband 1105 instead of on eyewear device 1102 may help better distribute the weight and heat generated by power source 1135.

As noted, some artificial-reality systems may, instead of blending an artificial reality with actual reality, substantially replace one or more of a user's sensory perceptions of the real world with a virtual experience. One example of this type of system is a head-worn display system, such as virtual-reality system 1200 in FIG. 12, that mostly or completely covers a user's field of view. Virtual-reality system 1200 may include a front rigid body 1202 and a band 1204 shaped to fit around a user's head. Virtual-reality system 1200 may also include output audio transducers 1206(A) and 1206(B). Furthermore, while not shown in FIG. 12, front rigid body 1202 may include one or more electronic elements, including one or more electronic displays, one or more inertial measurement units (IMUS), one or more tracking emitters or detectors, and/or any other suitable device or system for creating an artificial-reality experience.

Artificial-reality systems may include a variety of types of visual feedback mechanisms. For example, display devices in augmented-reality system 1100 and/or virtual-reality system 1200 may include one or more liquid crystal displays (LCDs), light emitting diode (LED) displays, microLED displays, organic LED (OLED) displays, digital light project (DLP) micro-displays, liquid crystal on silicon (LCoS) micro-displays, and/or any other suitable type of display screen. These artificial-reality systems may include a single display screen for both eyes or may provide a display screen for each eye, which may allow for additional flexibility for varifocal adjustments or for correcting a user's refractive error. Some of these artificial-reality systems may also include optical subsystems having one or more lenses (e.g., conventional concave or convex lenses, Fresnel lenses, adjustable liquid lenses, etc.) through which a user may view a display screen. These optical subsystems may serve a variety of purposes, including to collimate (e.g., make an object appear at a greater distance than its physical distance), to magnify (e.g., make an object appear larger than its actual size), and/or to relay (to, e.g., the viewer's eyes) light. These optical subsystems may be used in a non-pupil-forming architecture (such as a single lens configuration that directly collimates light but results in so-called pincushion distortion) and/or a pupil-forming architecture (such as a multi-lens configuration that produces so-called barrel distortion to nullify pincushion distortion).

In addition to or instead of using display screens, some of the artificial-reality systems described herein may include one or more projection systems. For example, display devices in augmented-reality system 1100 and/or virtual-reality system 1200 may include micro-LED projectors that project light (using, e.g., a waveguide) into display devices, such as clear combiner lenses that allow ambient light to pass through. The display devices may refract the projected light toward a user's pupil and may enable a user to simultaneously view both artificial-reality content and the real world. The display devices may accomplish this using any of a variety of different optical components, including waveguide components (e.g., holographic, planar, diffractive, polarized, and/or reflective waveguide elements), light-manipulation surfaces and elements (such as diffractive, reflective, and refractive elements and gratings), coupling elements, etc. Artificial-reality systems may also be configured with any other suitable type or form of image projection system, such as retinal projectors used in virtual retina displays.

The artificial-reality systems described herein may also include various types of computer vision components and subsystems. For example, augmented-reality system 1100 and/or virtual-reality system 1200 may include one or more optical sensors, such as two-dimensional (2D) or 3D cameras, structured light transmitters and detectors, time-of-flight depth sensors, single-beam or sweeping laser rangefinders, 3D LiDAR sensors, and/or any other suitable type or form of optical sensor. An artificial-reality system may process data from one or more of these sensors to identify a location of a user, to map the real world, to provide a user with context about real-world surroundings, and/or to perform a variety of other functions.

The artificial-reality systems described herein may also include one or more input and/or output audio transducers. Output audio transducers may include voice coil speakers, ribbon speakers, electrostatic speakers, piezoelectric speakers, bone conduction transducers, cartilage conduction transducers, tragus-vibration transducers, and/or any other suitable type or form of audio transducer. Similarly, input audio transducers may include condenser microphones, dynamic microphones, ribbon microphones, and/or any other type or form of input transducer. In some embodiments, a single transducer may be used for both audio input and audio output.

In some embodiments, the artificial-reality systems described herein may also include tactile (i.e., haptic) feedback systems, which may be incorporated into headwear, gloves, body suits, handheld controllers, environmental devices (e.g., chairs, floormats, etc.), and/or any other type of device or system. Haptic feedback systems may provide various types of cutaneous feedback, including vibration, force, traction, texture, and/or temperature. Haptic feedback systems may also provide various types of kinesthetic feedback, such as motion and compliance. Haptic feedback may be implemented using motors, piezoelectric actuators, fluidic systems, and/or a variety of other types of feedback mechanisms. Haptic feedback systems may be implemented independent of other artificial-reality devices, within other artificial-reality devices, and/or in conjunction with other artificial-reality devices.

By providing haptic sensations, audible content, and/or visual content, artificial-reality systems may create an entire virtual experience or enhance a user's real-world experience in a variety of contexts and environments. For instance, artificial-reality systems may assist or extend a user's perception, memory, or cognition within a particular environment. Some systems may enhance a user's interactions with other people in the real world or may enable more immersive interactions with other people in a virtual world. Artificial-reality systems may also be used for educational purposes (e.g., for teaching or training in schools, hospitals, government organizations, military organizations, business enterprises, etc.), entertainment purposes (e.g., for playing video games, listening to music, watching video content, etc.), and/or for accessibility purposes (e.g., as hearing aids, visual aids, etc.). The embodiments disclosed herein may enable or enhance a user's artificial-reality experience in one or more of these contexts and environments and/or in other contexts and environments.

As detailed above, the computing devices and systems described and/or illustrated herein broadly represent any type or form of computing device or system capable of executing computer-readable instructions, such as those contained within the modules described herein. In their most basic configuration, these computing device(s) may each include at least one memory device and at least one physical processor.

In some examples, the term “memory device” generally refers to any type or form of volatile or non-volatile storage device or medium capable of storing data and/or computer-readable instructions. In one example, a memory device may store, load, and/or maintain one or more of the modules described herein. Examples of memory devices include, without limitation, Random Access Memory (RAM), Read Only Memory (ROM), flash memory, Hard Disk Drives (HDDs), Solid-State Drives (SSDs), optical disk drives, caches, variations or combinations of one or more of the same, or any other suitable storage memory.

In some examples, the term “physical processor” generally refers to any type or form of hardware-implemented processing unit capable of interpreting and/or executing computer-readable instructions. In one example, a physical processor may access and/or modify one or more modules stored in the above-described memory device. Examples of physical processors include, without limitation, microprocessors, microcontrollers, Central Processing Units (CPUs), Field-Programmable Gate Arrays (FPGAs) that implement softcore processors, Application-Specific Integrated Circuits (ASICs), portions of one or more of the same, variations or combinations of one or more of the same, or any other suitable physical processor.

Although illustrated as separate elements, the modules described and/or illustrated herein may represent portions of a single module or application. In addition, in certain embodiments one or more of these modules may represent one or more software applications or programs that, when executed by a computing device, may cause the computing device to perform one or more tasks. For example, one or more of the modules described and/or illustrated herein may represent modules stored and configured to run on one or more of the computing devices or systems described and/or illustrated herein. One or more of these modules may also represent all or portions of one or more special-purpose computers configured to perform one or more tasks.

In addition, one or more of the modules described herein may transform data, physical devices, and/or representations of physical devices from one form to another. Additionally or alternatively, one or more of the modules recited herein may transform a processor, volatile memory, non-volatile memory, and/or any other portion of a physical computing device from one form to another by executing on the computing device, storing data on the computing device, and/or otherwise interacting with the computing device.

In some embodiments, the term “computer-readable medium” generally refers to any form of device, carrier, or medium capable of storing or carrying computer-readable instructions. Examples of computer-readable media include, without limitation, transmission-type media, such as carrier waves, and non-transitory-type media, such as magnetic-storage media (e.g., hard disk drives, tape drives, and floppy disks), optical-storage media (e.g., Compact Disks (CDs), Digital Video Disks (DVDs), and BLU-RAY disks), electronic-storage media (e.g., solid-state drives and flash media), and other distribution systems.

The process parameters and sequence of the steps described and/or illustrated herein are given by way of example only and can be varied as desired. For example, while the steps illustrated and/or described herein may be shown or discussed in a particular order, these steps do not necessarily need to be performed in the order illustrated or discussed. The various exemplary methods described and/or illustrated herein may also omit one or more of the steps described or illustrated herein or include additional steps in addition to those disclosed.

The preceding description has been provided to enable others skilled in the art to best utilize various aspects of the exemplary embodiments disclosed herein. This exemplary description is not intended to be exhaustive or to be limited to any precise form disclosed. Many modifications and variations are possible without departing from the spirit and scope of the present disclosure. The embodiments disclosed herein should be considered in all respects illustrative and not restrictive. Reference should be made to the appended claims and their equivalents in determining the scope of the present disclosure.

Unless otherwise noted, the terms “connected to” and “coupled to” (and their derivatives), as used in the specification and claims, are to be construed as permitting both direct and indirect (i.e., via other elements or components) connection. In addition, the terms “a” or “an,” as used in the specification and claims, are to be construed as meaning “at least one of.” Finally, for ease of use, the terms “including” and “having” (and their derivatives), as used in the specification and claims, are interchangeable with and have the same meaning as the word “comprising.” 

What is claimed is:
 1. A computer-implemented method comprising: executing, by a server-side hosted environment, a first application non-native to the server-side hosted environment, the executing comprising virtualizing hardware for the server-side hosted environment that supports the execution of the first application in the server-side hosted environment; receiving, by the server-side hosted environment by way of a network, an input data stream from a second application executing on a computing device; processing, by the server-side hosted environment and by the first application while executing in the virtualized hardware, the input data stream, the processing generating an output data stream; and outputting, by the server-side hosted environment and to the computing device by way of the network, the output data stream for use by the second application.
 2. The computer-implemented method of claim 1, wherein the first application comprises a video game.
 3. The computer-implemented method of claim 2, wherein the second application comprises a social media application that provides game play to an end user of the computing device.
 4. The computer-implemented method of claim 2, wherein the second application comprises a browser application that provides game play to an end user of the computing device.
 5. The computer-implemented method of claim 1, wherein a Web Real-Time Communication protocol stack is used to transfer data streams between the computing device and the server-side hosted environment.
 6. The computer-implemented method of claim 1, wherein the server-side hosted environment comprises one of: a mobile device OS emulator, or an OS virtual machine.
 7. The computer-implemented method of claim 6, wherein the mobile device OS emulator comprises an ANDROID™ OS emulator.
 8. The computer-implemented method of claim 6, where the OS virtual machine comprises a MICROSOFT® WINDOWS® virtual machine.
 9. The computer-implemented method of claim 1, wherein the server-side hosted environment comprises a cloud platform that incorporates edge computing.
 10. The computer-implemented method of claim 1, wherein virtualizing hardware for the server-side hosted environment that supports the execution of the first application in the server-side hosted environment comprises emulating a native environment suited to operate the first application.
 11. The computer-implemented method of claim 1, wherein virtualizing hardware for the server-side hosted environment that supports the execution of the first application in the server-side hosted environment comprises providing a virtual container in an operating system virtualization layer, the virtual container comprising a sandboxed execution environment for the first application by the server-side hosted environment.
 12. The computer-implemented method of claim 11, wherein virtualizing hardware for the server-side hosted environment that supports the execution of the first application in the server-side hosted environment further comprises dynamically provisioning one or more of the first application or the server-side hosted environment within the virtual container in response to a request to provision the first application.
 13. The computer-implemented method of claim 1, wherein the computing device comprises an artificial-reality system having a display for displaying the output data stream in the artificial-reality system.
 14. A system comprising: at least one physical processor; and physical memory comprising computer-executable instructions that, when executed by the physical processor, cause the physical processor to: execute a first application non-native to a server-side hosted environment, the executing of the first application comprising virtualizing hardware for the server-side hosted environment that supports the execution of the first application in the server-side hosted environment; receive, by way of a network, an input data stream from a second application executing on a computing device; process, by the first application while executing in the virtualized hardware, the input data stream, the processing generating an output data stream; and output, to the computing device by way of the network, the output data stream for use by the second application.
 15. The system of claim 14, wherein the first application comprises a video game.
 16. The system of claim 15, wherein the second application comprises one of a social media application that provides game play to an end user of the computing device or a browser application that provides game play to an end user of the computing device.
 17. The system of claim 14, wherein a Web Real-Time Communication protocol stack is used to transfer data streams between the computing device and the server-side hosted environment.
 18. The system of claim 14, wherein the server-side hosted environment comprises one of: a mobile device OS emulator, or an OS virtual machine.
 19. The system of claim 14, wherein the server-side hosted environment comprises a cloud platform that incorporates edge computing.
 20. A non-transitory computer-readable medium comprising one or more computer-executable instructions that, when executed by at least one processor of a server-side hosted environment, cause the server-side hosted environment to: execute a first application non-native to the server-side hosted environment, the executing of the first application comprising virtualizing hardware for the server-side hosted environment that supports the execution of the first application in the server-side hosted environment; receive, by way of a network, an input data stream from a second application executing on a computing device; process, by the first application while executing in the virtualized hardware, the input data stream, the processing generating an output data stream; and output, to the computing device by way of the network, the output data stream for use by the second application. 